Methods, systems, and media for presenting media content items using multiple devices

ABSTRACT

Mechanisms for presenting media content items using multiple devices are provided. In some embodiments, methods for presenting media content are provided that include: detecting an offer to initiate a purchase of a content item being presented using the media device, wherein the media device has not been authenticated with a content service that provides the content item; in response to detecting the offer to initiate the purchase of the content item when the media device has not been authenticated with the content service that provides the content item, causing the media device to be discoverable by one or more mobile devices that are connected to a same local area network as the media device; encoding offer data corresponding to the detected offer to initiate the purchase of the content item; in response to receiving a status request from a mobile device that is connected to the same local area network as the media device, transmitting the encoded offer data associated with the purchase of the content item to the mobile device, wherein the encoded offer data causes a payment user interface to be presented on the mobile device; receiving a cast request from the mobile device to cast the content item on the media device; and in response to the cast request, executing a receiver application on the media device that accepts the cast request from the mobile device and causes the content item to be presented using the media device.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of International Patent ApplicationNo. PCT/US2019/064210, filed Dec. 3, 2019, which is hereby incorporatedby reference herein in its entirety.

TECHNICAL FIELD

The disclosed subject matter relates to methods, systems, and media forpresenting media content items using multiple devices.

BACKGROUND

Many users want to watch media content associated with a video hostingor sharing services on media devices, such as their televisions or otherdisplay devices. It is often preferable or necessary to sign in to auser account associated with the service to access and view mediacontent. In particular, such users must be signed in to a user accountassociated with the service to purchase the media content for playbackon the media device. However, it is generally difficult to provide theuser account information, such as a username and a password, and/orpayment information, such as credit card information, in these types ofmedia devices. For example, using input devices like remote controls tosign in to a user account from the media device and/or complete apayment transaction from the media device can be time consuming and/orcumbersome.

Accordingly, it is desirable to provide methods, systems, and media forpresenting media content items using multiple devices.

SUMMARY

Methods, systems, and media for selecting formats for presenting mediacontent items using multiple devices are provided.

In accordance with some embodiments of the disclosed subject matter, amethod for presenting media content is provided, the method comprising:detecting an offer to initiate a purchase of a content item beingpresented using the media device, wherein the media device has not beenauthenticated with a content service that provides the content item; inresponse to detecting the offer to initiate the purchase of the contentitem when the media device has not been authenticated with the contentservice that provides the content item, causing the media device to bediscoverable by one or more mobile devices that are connected to a samelocal area network as the media device; encoding offer datacorresponding to the detected offer to initiate the purchase of thecontent item; in response to receiving a status request from a mobiledevice that is connected to the same local area network as the mediadevice, transmitting the encoded offer data associated with the purchaseof the content item to the mobile device, wherein the encoded offer datacauses a payment user interface to be presented on the mobile device;receiving a cast request from the mobile device to cast the content itemon the media device; and, in response to the cast request, executing areceiver application on the media device that accepts the cast requestfrom the mobile device and causes the content item to be presented usingthe media device. Thus, the method may overcome the technicaldifficulties (e.g. the required time, and the risk of errors) ofentering data into a content service for providing content to a mediadevice by relying entirely on a data entry device associated with themedia device (e.g. a remote control device). It does this by takingadvantage of the typically more sophisticated data entry capability of amobile device. This is achieved in a secure manner, despite theadditional involvement of the mobile device.

In some embodiments, the media device is executing a media playbackapplication and the mobile device is executing a corresponding mediaplayback application, the media playback application transmits theencoded offer data to the corresponding media playback applicationexecuting on the mobile device, and, in response to transmitting theencoded offer data to the mobile device, the media device inhibits thetransmission of the encoded offer data to remaining mobile devices thatare connected to the same local area network.

In some embodiments, the encoded offer data causes the mobile device toretrieve corresponding human-readable information from a server, wherethe human-readable information is presented in the payment userinterface on the mobile device.

In some embodiments, the method further comprises receivingauthentication information from the mobile device, wherein theauthentication information corresponds to a user account that was usedto complete the purchase via the payment user interface on the mobiledevice. In some embodiments, the authentication information causes themedia device to retrieve a corresponding authentication token from anauthentication server, wherein the corresponding authentication tokenauthenticates the user account on the media device.

In some embodiments, the cast request indicates that the mobile deviceis authorized to play back the content item.

In accordance with some embodiments of the disclosed subject matter, asystem for presenting media content is provided, the system comprising amemory and a hardware processor that, when executing computer-executableinstructions stored in the memory, is configured to: detect an offer toinitiate a purchase of a content item being presented using the mediadevice, wherein the media device has not been authenticated with acontent service that provides the content item; in response to detectingthe offer to initiate the purchase of the content item when the mediadevice has not been authenticated with the content service that providesthe content item, cause the media device to be discoverable by one ormore mobile devices that are connected to a same local area network asthe media device; encode offer data corresponding to the detected offerto initiate the purchase of the content item; in response to receiving astatus request from a mobile device that is connected to the same localarea network as the media device, transmit the encoded offer dataassociated with the purchase of the content item to the mobile device,wherein the encoded offer data causes a payment user interface to bepresented on the mobile device; receive a cast request from the mobiledevice to cast the content item on the media device; and, in response tothe cast request, execute a receiver application on the media devicethat accepts the cast request from the mobile device and causes thecontent item to be presented using the media device.

In accordance with some embodiments of the disclosed subject matter, acomputer program product (such as a non-transitory computer-readablemedium or an item of software for download over a communication network)containing computer executable instructions that, when executed by aprocessor, cause the processor to perform a method for presenting mediacontent is provided, the method comprising: detecting an offer toinitiate a purchase of a content item being presented using the mediadevice, wherein the media device has not been authenticated with acontent service that provides the content item; in response to detectingthe offer to initiate the purchase of the content item when the mediadevice has not been authenticated with the content service that providesthe content item, causing the media device to be discoverable by one ormore mobile devices that are connected to a same local area network asthe media device; encoding offer data corresponding to the detectedoffer to initiate the purchase of the content item; in response toreceiving a status request from a mobile device that is connected to thesame local area network as the media device, transmitting the encodedoffer data associated with the purchase of the content item to themobile device, wherein the encoded offer data causes a payment userinterface to be presented on the mobile device; receiving a cast requestfrom the mobile device to cast the content item on the media device;and, in response to the cast request, executing a receiver applicationon the media device that accepts the cast request from the mobile deviceand causes the content item to be presented using the media device.

In accordance with some embodiments of the disclosed subject matter, asystem for presenting media content is provided, the system comprising:means for detecting an offer to initiate a purchase of a content itembeing presented using the media device, wherein the media device has notbeen authenticated with a content service that provides the contentitem; in response to detecting the offer to initiate the purchase of thecontent item when the media device has not been authenticated with thecontent service that provides the content item, means for causing themedia device to be discoverable by one or more mobile devices that areconnected to a same local area network as the media device; means forencoding offer data corresponding to the detected offer to initiate thepurchase of the content item; in response to receiving a status requestfrom a mobile device that is connected to the same local area network asthe media device, means for transmitting the encoded offer dataassociated with the purchase of the content item to the mobile device,wherein the encoded offer data causes a payment user interface to bepresented on the mobile device; means for receiving a cast request fromthe mobile device to cast the content item on the media device; and inresponse to the cast request, means for executing a receiver applicationon the media device that accepts the cast request from the mobile deviceand causes the content item to be presented using the media device.

BRIEF DESCRIPTION OF THE DRAWINGS

Various objects, features, and advantages of the disclosed subjectmatter can be more fully appreciated with reference to the followingdetailed description of the disclosed subject matter when considered inconnection with the following drawings, in which like reference numeralsidentify like elements.

FIG. 1 shows an illustrative example of a process for mobiledevice-assisted purchasing of content items for playback using aconnected media device, where encoded offer data is broadcast to one ormore mobile devices to purchase a content item, in accordance with someembodiments of the disclosed subject matter.

FIG. 2 shows an illustrative example of a process for using a mobiledevice to detect the presence of a media device, presenting a userinterface for completing a payment transaction associated with thepurchase of a content item, and casting the content item forpresentation using the media device in accordance with some embodimentsof the disclosed subject matter.

FIG. 3 shows an illustrative user interface for proceed through apayment transaction for purchasing the content item on the mobile devicethat is connected to the media device and for presentation on the mediadevice in accordance with some embodiments of the disclosed subjectmatter.

FIG. 4 shows a schematic diagram of an illustrative system suitable forimplementation of mechanisms described herein for presenting mediacontent items using multiple devices in accordance with some embodimentsof the disclosed subject matter.

FIG. 5 shows a detailed example of hardware that can be used in a serverand/or a user device of FIG. 4 in accordance with some embodiments ofthe disclosed subject matter.

DETAILED DESCRIPTION

In accordance with various embodiments, mechanisms (which can includemethods, systems, and media) for presenting media content items usingmultiple devices are provided.

In some embodiments, the mechanisms described herein can detect that anoffer to initiate a purchase of a content item is being presented usingthe media device. For example, while navigating through multiple contentitems being presented on a media device (e.g., using a remote controldevice), the mechanisms can detect that a selected content item isassociated with an offer to provide a payment in exchange for playingback the content item. In a more particular example, while navigatingthrough multiple content items being presented on the media device, themechanisms can detect that a selected content item is associated with a“buy” button or a “rent” button. In some embodiments, upon detecting thepresented offer, the mechanisms can also determine that the media devicehas not been authenticated to a service that is providing the contentitem. For example, the media device has not signed into a service and,as such, user payment information is not stored for use in purchasing orother paying for the selected content item.

It should be noted that, in some embodiments, the media device isconnected to a display device and the display device presents the userinterface for navigating through multiple content items and a mediaplayer for playing back one of the content items.

In some embodiments, in response to detecting the offer to initiate thepurchase of the content item when the media device has not beenauthenticated with the content service that provides the content item,the mechanisms can cause the media device to be made discoverable by oneor more mobile devices that are connected to a same local area networkas the media device. For example, the media device can implement theserver side of the Discovery And Launch (DIAL) protocol to broadcast itspresence to devices connected to the same local area network. Incontinuing this example, one or more mobile devices connected to thesame local area network can implement the client side of the DIALprotocol, where the mobile device can discover the DIAL service on themedia device on the local area network and can launch applications on aDIAL server. In a more particular example, the mobile device can, usinga media playback application executing on the mobile device, use theDIAL server to prompt the media device to launch a corresponding mediaplayback application. This can include passing an IP/port correspondingto the media playback application, a URL to the media playbackapplication, and/or any other suitable information. It should be notedthat the DIAL protocol allows for the transfer of arbitrary data betweenthe media device and the mobile device. Accordingly, in someembodiments, the media playback application executing on the mediadevice can return additional information to the DIAL server via anadditionalData field.

In some embodiments, the media device can encode offer data associatedwith the purchase of the content item for placement in theadditionalData field. This can include, for example, a contentidentifier, a description of the content item, a price associated withplaying back the content item, the type of purchase, a duration forplaying back the content item, an application that is used to playbackthe content item, etc.

It should be noted that, in some embodiments, the encoded offer data cancause the mobile device to retrieve human-readable information about thecorresponding offer from a server (e.g., a media server, a paymentserver, etc.). In return, one or more payment user interfaces can bepresented on the mobile device that provide the human-readableinformation about the corresponding offer and proceed through a paymenttransaction for purchasing the content item.

In some embodiments, upon completing the payment transaction, the mobiledevice can transmit a cast request to cast the content item on the mediadevice. For example, in response to completing the payment transactionand receiving an indication that the mobile device is authorized toplayback the content item, the mobile device can be configured toautomatically cast the content item for playing back on the mediadevice. In another example, in response to receiving the cast request,the media device can execute a media playback application or any othersuitable receiver application that accepts the cast request from themobile device and causes the content item to be presented using themedia device. In a more particular example, the cast request can includea URL or any other suitable content identifier that allows the mediadevice to retrieve the content item for playback.

Additionally to the cast request, in some embodiments, authenticationinformation that corresponds to the user account that was used tocomplete the purchase of the content item via the payment user interfaceon the mobile device can be retrieved. For example, the authenticationinformation can cause the media device to retrieve a correspondingauthentication token from an authentication server, where thecorresponding authentication token authenticates the user account on themedia device.

These mechanisms can, for example, allow a user to complete atransaction for the content item without being signed in or otherwiseauthenticated on the media device and without requiring the user toinput authentication information or payment information using an inputdevice associated with the media device (e.g., a remote control device,an on-screen keyboard, etc.) while allowing the user to watch thepurchased content item on the media device. These mechanisms can alsoallow other users (e.g., users having nearby mobile devices) to purchasethe content item for playback on the media device (e.g., using a useraccount that is not associated with the media device). These mechanismscan further allow payment information and other user information to beentered and/or transmitted using a private device as opposed to themedia device where there may be additional viewers.

These and other features for presenting media content items usingmultiple devices are described further in connection with FIGS. 1-5.

Turning to FIG. 1, an illustrative example of a process 100 for mobiledevice-assisted purchasing of content items for playback using aconnected media device in accordance with some embodiments of thedisclosed subject matter is shown. As illustrated, blocks of process 100can be executed by a media device and/or any other suitable computingdevice(s). For example, the media device can be a user device with noinput devices and/or input device that make entry of, among otherthings, payment information and user credential information difficult,such as a television device, a household appliance, and/or any othersuitable display device.

It should be noted that, although the embodiments described hereingenerally relate to a content item being presented by a media device,this is merely illustrative. In some embodiments, the media device canbe a media rendering device that is connected to a display device, wherethe display device receives instructions from the media rendering deviceto present, among other things, user interfaces associated with a mediaplayback application for navigating through multiple content items and amedia player for playing back one of the content items.

Process 100 can begin at 110 by detecting that an offer to initiate apurchase of a content item is being presented using the media device(e.g., on a display associated with the media device). For example,while navigating through multiple content items being presented on amedia device (e.g., using a remote control device or any other suitableinput device), process 100 can detect that a selected content item isassociated with an offer to provide a payment in exchange for playingback the content item. In a more particular example, while navigatingthrough multiple content items being presented on the media device,process 100 can detect that a selected content item is associated with a“buy” button or a “rent” button. In another more particular example,while navigating through multiple content items, each content item beingpresented using the media device can be associated with purchaseinformation (e.g., $2.99 for viewing the content item within 48 hours ofpurchase). In continuing this example, process 100 can detect that themedia device has navigated to a page in which the user of the mediadevice is provided with an opportunity to initiate the purchase of acontent item (e.g., by selecting a “buy” button on an on-screeninterface, by selecting a “buy” button on a remote control device,etc.).

In some embodiments, process 100 can receive an indication of aninitiation of a purchase of a content for presentation by the mediadevice. For example, process 100 can receive an indication that a userhas selected a content item for playback that has associated purchaseinformation. In another example, process 100 can receive a purchaseindicator in response to accessing a page using a media playbackapplication executing on the media device in which the user can initiatethe purchase of a content item.

In some embodiments, process 100 can also determine that the mediadevice has not been authenticated to a service that is providing thecontent item. For example, process 100 can determine that the mediadevice has not been signed into a suitable service in which the user caninput payment information and/or user account information. In a moreparticular example, the media playback application executing on themedia device can determine that a user account associated with a contentprovider has not been authenticated on the media device. As such, inorder to proceed with the purchase of the content item, and/or that auser account associated with a payment service has not beenauthenticated on the media device.

At 120, in response to detecting the offer to initiate the purchase ofthe content item being presented by the media device and in response todetermining that the media device has not been authenticated with thecontent service that provides the content item, process 100 can causethe media device to be made discoverable by one or more mobile devicesthat are connected to a same local area network as the media device. Forexample, the media device can implement the server side of the DiscoveryAnd Launch (DIAL) protocol to broadcast its presence to devicesconnected to the same local area network. In continuing this example,one or more mobile devices connected to the same local area network canimplement the client side of the DIAL protocol, where the mobile devicecan discover the DIAL service on the media device on the local areanetwork and can launch applications on a DIAL server.

It should be noted that a media playback application executing on themedia device can create a communication channel with a correspondingmedia playback application executing on the mobile device. For example,using this communication channel, the media playback applicationexecuting on the mobile device can discover the DIAL service implementedon the media device. The media playback application executing on themobile device can then use the DIAL protocol to query the media deviceto launch a corresponding media playback application on the media deviceor to query whether the corresponding media playback application hasalready been launched on the media device.

In continuing this example, it should be noted that the DIAL protocolcan allow for the transfer of arbitrary data between the media deviceand the mobile device. The DIAL server can transmit, for example, a URLor other suitable information to the media playback application, whichthe media playback application executing on the media device can use torelay information to the DIAL server.

In some embodiments, at 130, process 100 can encode offer dataassociated with purchasing the content item. Offer data can include, forexample, a content identifier, a description of the content item, aprice associated with playing back the content item, the type ofpurchase, a duration for playing back the content item, an applicationthat is used to playback the content item, a location identifierpointing to where the user has an opportunity to purchase the contentitem, etc. It should be noted that such encoded offer data can betransmitted to the mobile device as additional information in anadditionalData field.

In some embodiments, at 140, process 100 can transmit the encoded offerdata to a mobile device. For example, in response to a mobile devicethat is executing a DIAL client discovering a DIAL server on a mediadevice, the DIAL client executing on the mobile device can transmit arequest to determine whether a media playback application is availableon the media device, is executing on the media device, and/or otherinformation regarding the status of the media playback application onthe media device. In response, the DIAL server response can indicatethat the media playback application is already running and can includeadditional data, which contains the encoded offer data described above.It should be noted that, in some embodiments, the additional data canalso enable the media playback application executing on the mobiledevice to communicate with the running instance of the media playbackapplication executing on the media device.

In a more particular example, a media playback application launched orrunning on the media device can transmit data, including theadditionalData field, to a DIAL server. Such data can also include, forexample, device information, application state information, networkinformation, etc. In turn, the DIAL server can communicate the data toDIAL clients that connect to the DIAL server. For example, in responseto detecting the offer to initiate the purchase of the content itembeing presented by the media device and in response to determining thatthe media device has not been authenticated with the content servicethat provides the content item, process 100 can cause the media playbackapplication executing on the media device to include the encoded offerdata in the additionalData field and can post the encoded offer data tothe DIAL server or otherwise broadcast the encoded offer data to a DIALclient executing on a mobile device.

In some embodiments, the media device can determine whether to transmitthe encoded offer data to the mobile device. For example, the mediadevice can use any suitable criterion to determine whether to transmitthe encoded offer data to the mobile device. In a more particularexample, the media device can determine that there are multiple mobiledevices in proximity of the media device and that are connected to thesame local area network. In continuing this example, the media devicecan determine whether a preferred mobile device is one of the multiplemobile devices—e.g., a preferred mobile device that has been usedgreater than a threshold number of times for purchasing content itemscan be selected to receive the encoded offer data, a mobile device thatis associated with a particular type of user (e.g., a minor, a user thatis not associated with a payment account, etc.) can be excluded frombeing selected to receive the encoded offer data, a mobile device thatis currently authenticated with a payment service can be selected toreceive the encoded offer data, etc.

In some embodiments, the media device can determine a probability as towhether a mobile device that receives the encoded offer data is likelyto complete the payment process in purchasing the content item. Forexample, a mobile device that is associated with a child user can bedetermined to have a low probability of completing the payment processwhile a mobile device that is associated with a user that has purchasedmultiple content items using the mobile device can be designated ashaving a high probability of completing the payment process.

In continuing this example, in response to a mobile device receiving theencoded offer data, process 100 can cause the media device to inhibitthe transmission of the encoded offer data to any remaining mobiledevices that are connected to the same local area network. As such,additional mobile devices that are connected to the same local areanetwork, that have discovered the DIAL service executing on the mediadevice, and that have requested status information relating to a mediaplayback application executing on the media device may not receive theencoded offer data in the additionalData field. This can, for example,prevent the purchase of the content item for playback on the mediadevice from being initiated on multiple devices (e.g., mobile device offriend A and mobile device of friend B).

It should be noted that, in some embodiments, in response to determiningthat the mobile device has not completed the purchase of the contentitem (e.g., the purchase has not been completed within a thresholdamount of time, the mobile device has abandoned the purchase of thecontent item, etc.), process 100 can cause the media device to continueproviding the encoded offer data in the form of additional data.

It should also be noted that, in some embodiments, concurrently withencoding the offer data and transmitting the encoded offer data to amobile device, process 100 can present a payment interface on the mediadevice for inputting payment information to purchase the content item.For example, in response to selecting the “buy” option in 110, the mediadevice can present a user interface for completing the paymenttransaction on the media device.

As described below in FIG. 2, the mobile device can receive the encodedoffer data and can proceed with the purchase of the content item.

At 150, in response to the mobile device completing the purchase of thecontent item (e.g., via a payment service) and in response to the mobiledevice receiving authorization to playback the content item, process 100can retrieve an indication to cast the content item from the mobiledevice for presentation by the media device.

In a more particular example, casting technology refers to contentstreaming and playback that includes a first device that identifies thecontent item to be played and a second device that provides the playbackof the identified content item. For example, the first device is themobile device that completed the purchase of the content item andreceived authorization to playback the purchased content item and thesecond device is the media device that plays back the purchased contentitem. In casting technology, video encoding of the content item is notperformed by the mobile device. Rather, the media playback applicationexecuting on the mobile device can transmit a universal resourceidentifier (URI) (e.g., a universal resource locator (URL)) for thecontent item to the media device, and the media device can use the URIto obtain the content item from a content provider server via anInternet connection over a network. The media device can receive thecontent item and can stream the content item from the URI directly toone or more output devices (e.g., a television, a home theater audiosystem, etc.).

In some embodiments, alternatively to casting the content item from themobile device to the media device, the mobile device can implementmirroring technology in which the mobile device can receive the contentitem as a media stream from the content provider server over acommunications network (e.g., in response to the mobile devicecompleting the purchase of the content item (e.g., via a paymentservice) and in response to the mobile device receiving authorization toplayback the content item) and can repackage the media stream as are-formatted media stream for the media device. The mobile device canstream the re-formatted stream over a wireless local area network to themedia device. The media device can then output the content item to oneor more output devices (e.g., a television, a home theater audio system,etc.).

In some embodiments, as described below in connection with FIG. 2,authentication information corresponding to the user account that wasused on the mobile device to purchase the content item can betransmitted to the media device. The media device can use theauthentication information to retrieve a corresponding authenticationtoken from an authentication server, where the correspondingauthentication token authenticates the user account on the media device.

Turning to FIG. 2, an illustrative example 200 of a process for mobiledevice-assisted purchasing of content items in which the mobile devicereceives the encoded offer data and proceeds with the purchase of thecontent item in accordance with some embodiments of the disclosedsubject matter is shown. As illustrated, blocks of process 200 can beexecuted by a mobile device and/or any other suitable computingdevice(s). For example, the mobile device can be a user device thatsupports casting technology or mirroring technology such that, uponcompleting the payment process in which the content item has beenpurchased and the mobile device is authorized to receive and playbackthe content item, the mobile device can cause the content item to bepresented by the media device for output on any suitable output device(e.g., a television, a home theater audio system, etc.).

Process 200 begins at 210 with the mobile device associating orconnecting with a local network (e.g., a local area network, a wirelesslocal area network, a wired/wireless local area network, or any othersuitable network). For example, the mobile device can connect with awireless local area network having multiple networked media devices. At220, process 200 can detect, using a media playback applicationexecuting on the mobile device, the presence of a media device. Forexample, using the Discovery And Launch (DIAL) protocol, the mobiledevice can implement the client side of the DIAL protocol and candiscover the DIAL service on the media device. The mobile device can,for example, create a communication channel to exchange messages betweena media playback application executing on the mobile device and acorresponding media playback application executing on the media device.

At 230, in response to discovering the DIAL service on the media device,process 200 can receive, from the media device, status informationrelating to a corresponding media playback application executing on themedia device. For example, the DIAL client executing on the mobiledevice can transmit a request to determine whether a media playbackapplication is available on the media device, is executing on the mediadevice, and/or other information regarding the status of the mediaplayback application on the media device. In response, the DIAL serverresponse can indicate that the media playback application is alreadyrunning and can include additional data, which contains the encodedoffer data relating to the purchase of the content item described above.

As described above, the encoded offer data in the additionalData fieldcan include, for example, a content identifier, a description of thecontent item, a price associated with playing back the content item, thetype of purchase, a duration for playing back the content item, anapplication that is used to playback the content item, a locationidentifier pointing to where the user has an opportunity to purchase thecontent item, etc.

At 240, in response to receiving the encoded offer data, process 200 cantransmit a request to a server (e.g., a media server, a payment server,etc.) to obtain human-readable offer information corresponding to theencoded offer data. At 250, process 200 can use the human-readable offerinformation from the server to generate a user interface for presentingthe offer and one or more user interfaces for proceeding through apayment transaction for purchasing the content item. In a moreparticular example, the human-readable offer information can be combinedwith information relating to the selected content item to generate auser interface for initiating the payment process on the mobile device.An illustrative example of a user interface that presents the offer andprovides the user of the mobile device with an opportunity to proceedthrough the payment process on the mobile device is shown in FIG. 3.

At 260, in response to completing the payment process for the contentitem on the mobile device, process 200 can receive an authorization tostream or otherwise playback the content item on the mobile device. Forexample, the mobile device can receive a confirmation interfaceindicating that the payment process for the content item has beencompleted. In continuing this example, a play interface element or anyother suitable playback element can activate to allow the user toplayback the content item on the mobile device.

At 270, process 270 can cause the purchased content item to be casted tothe media device. For example, in some embodiments, the mobile device,upon receiving authorization to play back the content item, canautomatically transmit a cast request to the media device that initiallyreceived the offer to purchase the content item. In another example, insome embodiments, the mobile device, upon receiving authorization toplay back the content item, can present an instruction directing theuser of the mobile device to select a cast option to cast the purchasedcontent item to the media device.

As described above, in response to casting the content item from themobile device to the media device, the media playback applicationexecuting on the mobile device can transmit a universal resourceidentifier (URI) (e.g., a universal resource locator (URL)) for thecontent item to the media device, and the media device can use the URIto obtain the content item from a content provider server via anInternet connection over a network. The media device can receive thecontent item and can stream the content item from the URI directly toone or more output devices (e.g., a television, a home theater audiosystem, etc.).

As also described above, alternatively to casting the content item fromthe mobile device to the media device, the mobile device can implementmirroring technology in which the mobile device can receive the contentitem as a media stream from the content provider server over acommunications network (e.g., in response to the mobile devicecompleting the purchase of the content item (e.g., via a paymentservice) and in response to the mobile device receiving authorization toplayback the content item) and can repackage the media stream as are-formatted media stream for the media device. The mobile device canstream the re-formatted stream over a wireless local area network to themedia device. The media device can then output the content item to oneor more output devices (e.g., a television, a home theater audio system,etc.).

Additionally to causing the content item to be presented on the mediadevice without requiring the user to authenticate a user account (e.g.,associated with a content provider service, associated with a paymentservice, etc.), process 200 can authenticate the media device using themobile device. For example, concurrently with instructing that apurchase content item is cast from the mobile device for playback on anoutput device associated with the media device, the mobile device canalso transmit a message indicating that a user account that has beenauthenticated on the mobile device is to also be used for authenticationon the media device.

In some embodiments, the mobile device can transmit a message to themedia device indicating that a user account is to be logged into fromthe mobile device. For example, the user account can be the user accountassociated with a content provider service. In another example, the useraccount can be the user account that was used to proceed through thepayment process in purchasing the content item.

Note that, in some embodiments, the mobile device can initiateauthentication of a user account on the media device using usercredentials on the mobile device in response to determining that mediadevice is a particular type of user device (e.g., a television, a gameconsole, a home theater audio system, a set-top box, and/or any othersuitable type of device). As a more particular example, in someembodiments, the mobile device can determine a device type associatedwith the media device, and can identify one or more user accounts thathave been logged in to with the mobile device that are suitable useraccounts to be logged in to from the media device based on thedetermined device type of the media device. As a specific example, in aninstance where the mobile device determines that the media device is adisplay device, the mobile device can determine that a user accountassociated with a video sharing service is a candidate user account tobe logged in to on the media device using user credentials associatedwith the mobile device.

In some embodiments, a device type and/or a device category (e.g.,television, game console, set-top box, video camera, printer, and/or anyother suitable device type) can be determined using any suitabletechnique(s). For example, in some embodiments, the mobile device candetect the presence of one or more devices, such as a television device,for authenticating with a user account logged in on the mobile device.For example, device discovery of a nearby device can be initiated on thelocal area network to which the mobile device is connected. It should benoted that device discovery can be initiated by the mobile device at anysuitable time and for any suitable reason or reasons. For example, anapplication executing on the mobile device can initiate device discoveryto determine whether the mobile device is on the same network as themedia device (e.g., a television device). In a more particularembodiment, the mobile device can execute a full discovery protocol onthe network for determining the details of any devices found on thecurrent network. The full discovery protocol can include transmitting amulticast message to all devices on the network requesting devicedetails from the devices on the network. Additionally, the multicastmessage can be addressed to certain types of devices. In someembodiments, the mobile device can wait a predetermined amount of timefor responses to the multicast message. Additionally, in someembodiments, the full discovery protocol can include requestingadditional device details from devices that responded by sending amessage to an address and/or location included in a reply by the deviceto the multicast message. Such additional details can include a name ofthe device, a manufacturer of the device, a model name of the device, amodel number of the device, a model description of the device, a serialnumber of the device, and/or any other suitable device informationassociated with the device. In some embodiments, a device type or devicecategory (e.g., television, game console, set-top box, etc.) and/ordescription of the device's capabilities can be included in the responseto the message.

In some embodiments, the mobile device can present a first userinterface that requests approval to initiate authentication of the mediadevice. In response to a user of the mobile device providing an approvalto initiate authentication of a user account on the media device (e.g.,“Would you like to also log in to this account on the connectedtelevision?” or a prompt to select a user account for authenticating onthe media device), the mobile device can transmit an authorizationrequest to the media device.

In some embodiments, the media device can transmit a request to anauthorization server in response to receiving the authorization requestfrom the mobile device. In some embodiments, the request can include anysuitable information, such as information related to a connection of themobile device to a device association server (e.g., an identifierassociated with the mobile device, and/or any other suitableinformation), information related to a configuration of the mobiledevice (e.g., a manufacturer and/or model associated with the mobiledevice, an operating system associated with the mobile device, and/orany other suitable configuration information), information related to auser of the mobile device (e.g., one or more usernames associated withthe mobile device, and/or any other suitable information), and/or anyother suitable identifying information. In a more particular example, insome embodiments, the request can indicate an identifier associated withthe particular user account that is to be logged in to. As a moreparticular example, the request can indicate an identity of a serviceassociated with the user account (e.g., a name of a social networkingsite, a name of a video sharing site, and/or any other suitableidentity). As yet another more particular example, the request canindicate any suitable information associated with the media device, suchas an Internet Protocol (IP) address associated with the media device, alocation of the media device, and/or any other suitable information.

In some embodiments, the authorization server can transmit a messageincluding authentication data to the media device that corresponds to anexisting session associated with the user account and associated withthe mobile device. In some embodiments, the authentication data caninclude any suitable information, such as a random sequence ofcharacters (e.g., letters, numbers, any/or any other suitable charactersor combination of characters) of any suitable length (e.g., fourcharacters, eight characters, sixteen characters, and/or any othersuitable length). For example, in some embodiments, the authenticationdata can include an encrypted token associated with a current session ofthe user account established by the mobile device.

In some embodiments, the authorization server can transmit theauthentication data in connection with a Uniform Resource Locator (URL)that identifies a page that can be used to sign in to the user account.For example, in some embodiments, the authentication data can beembedded within a query string of the URL. As another example, in someembodiments, the URL can be included in the message transmitted to themedia device.

Additionally or alternatively, in some embodiments, the authenticationdata can indicate any suitable identifying information corresponding tothe mobile device and/or the user account. For example, in someembodiments, the authentication data can indicate information about themobile device (e.g., an identifier of a user associated with the mobiledevice, an identifier of a manufacturer of the mobile device, anidentifier of a product number associated with the mobile device, and/orany other suitable information). As another example, in someembodiments, the authentication data can indicate information associatedwith the user account (e.g., a date and/or time the user account waslast accessed from the mobile device, a Media Access Control (MAC)address associated with a connection last used to access the useraccount from the mobile device, and/or any other suitable information).In some embodiments, the authentication data can be encrypted using anysuitable protocol(s).

In some embodiments, the media device can transmit the authenticationdata included in the received message to the mobile device. In someembodiments, the media device can perform any suitable processing on thereceived message to extract the authentication data prior totransmitting the authentication data to the mobile device. For example,in some embodiments, the media device can extract a particular portionof the received message that contains the authentication data. As a moreparticular example, in instances where the received message includes aURL and the authentication data, the media device can extract theauthentication data from the URL.

In response to receiving the authentication data, the mobile device canpresent a user interface requesting authorization to authenticate themedia device. In some embodiments, the mobile device can identify one ormore user accounts that can be used by the media device. In some suchembodiments, the user interface can further request that a user select aparticular user account to be used by the media device.

In some embodiments, the mobile device can transmit informationassociated with the user account to the media device in response todetermining that the media device is to be authenticated. In someembodiments, the transmitted information can indicate that the mediadevice is permitted to access the user account using login informationassociated with the mobile device. In such embodiments, the transmittedinformation can include an indicator (e.g., a Boolean, an integer, aflag, and/or any other suitable type of indicator) whose value indicatesthat permission has been granted to access the user account. In someembodiments, the transmitted information can include any other suitableinformation, such as an indication of which of multiple user accounts isto be used by the media device.

In some embodiments, the media device can request an authenticationtoken from the authorization server based on the received information.In some embodiments, the media device can log in to the user account,for example, using the URL received from the authentication server. Insome embodiments, the media device can then request the authenticationtoken in response to determining that the user account has beensuccessfully logged in to. Alternatively, in some embodiments, the mediadevice can transmit the received information to the authorization server(e.g., transmit an indication that the mobile device has grantedpermission for the media device to log in to the user account usingcredentials associated with the mobile device), and can request that theauthorization server establish a session associated with the mediadevice and the user account and transmit the authorization token inresponse to establishing the session.

In some embodiments, the authorization server can transmit theauthentication token to the media device. In some embodiments, theauthentication token can be used for any suitable purposes. For example,in some embodiments, the authentication token can be used to indicatethat the user account has been signed in to by the media device, therebyallowing the user account to remain signed in to on the media device ininstances where a particular application is closed.

Turning to FIG. 4, an illustrative example 400 of hardware for mobiledevice-assisted purchasing of content items for playback using aconnected media device that can be used in accordance with someembodiments of the disclosed subject matter is shown. As illustrated,hardware 400 can include a server 402, a communication network 404,and/or one or more user devices 406, such as a mobile device 408 and amedia device 410.

Server 402 can be any suitable server(s) for storing information, data,programs, media content, and/or any other suitable content. In someembodiments, server 402 can perform any suitable function(s). Forexample, in some embodiments, server 402 can be any suitable contentserver for storing content and transmitting the content to a user devicefor presentation. For example, in some embodiments, server 402 can be aserver that transmits media content to user device 406 via communicationnetwork 404. It should be noted, however, that, in some embodiments,media content can be local media content that is stored on a suitablestorage device (e.g., a memory) associated with user device 406, such asmobile device 408. In continuing this example, local media content canbe transmitted from a storage device associated with mobile device 408to media device 410. Additionally or alternatively, local media contentmay have been downloaded and stored in a suitable storage device fromserver 402 or any other suitable device (e.g., in peer-to-peer filesharing). In some embodiments, the content on server 402 can be anysuitable content, such as a web page, video content, audio content,movies, television programs, live-streamed content, audiobooks, and/orany other suitable type of content.

In some embodiments, server 402 can be any suitable server(s) foridentifying an existing session associated with a user account and themobile device and transmitting authentication data corresponding to theidentified session. For example, in some embodiments, server 402 canreceive an authentication request from media device 410 and can identifythe existing session in response to receiving the authenticationrequest. As another example, in some embodiments, server 402 cangenerate authentication data and transmit the generated authenticationdata to media device 410. As yet another example, in some embodiments,server 402 can receive authentication requests that include usercredentials (e.g., usernames, passwords, and/or any other suitable usercredentials) corresponding to mobile device 408 (and/or any othersuitable user device) and can establish sessions of a corresponding useraccount in response to receiving the user credentials.

In some embodiments, server 402 can be any suitable server(s) forestablishing a communication channel between mobile device 408 and mediadevice 410. For example, in some embodiments, mobile device 408 andmedia device 410 can each connect to device association server 402, anddevice association server 402 can transmit messages between mobiledevice 408 and media device 410.

Communication network 404 can be any suitable combination of one or morewired and/or wireless networks in some embodiments. For example,communication network 404 can include any one or more of the Internet,an intranet, a wide-area network (WAN), a local-area network (LAN), awireless network, a digital subscriber line (DSL) network, a frame relaynetwork, an asynchronous transfer mode (ATM) network, a virtual privatenetwork (VPN), and/or any other suitable communication network. Userdevices 406 can be connected by one or more communications links (e.g.,communications links 412) to communication network 404 that can belinked via one or more communications links (e.g., communications links414) to server 402. The communications links can be any communicationslinks suitable for communicating data among user devices 406 and server402 such as network links, dial-up links, wireless links, hard-wiredlinks, any other suitable communications links, or any suitablecombination of such links.

In some embodiments, mobile device 408 can be any suitable user devicefor receiving encoded offer data corresponding to an offer beingprovided on a connected media device 410, presenting user interfaces forproceeding through a payment process for purchasing a content item forplayback on media device 410, transmitting messages to media device 410,casting the purchased content item for playback on media device 410,and/or any other suitable functions. In some embodiments, media device410 can be any suitable device for encoding offer data, presentingreceived content, and/or performing any other suitable functions. Insome embodiments, user devices 406 can be any suitable type of userdevices. For example, in some embodiments, user devices 406 can beimplemented as a mobile device, such as a smartphone, mobile phone, atablet computer, a wearable computer, a laptop computer, a vehicle(e.g., a car, a boat, an airplane, or any other suitable vehicle)entertainment system, a portable media player, and/or any other suitablemobile device. As another example, in some embodiments, user devices 406can be implemented as a non-mobile device, such as a desktop computer, aset-top box, a television, a streaming media player, a game console, aspeaker, home entertainment device, a media playback device, and/or anyother suitable non-mobile device.

In a more particular example, user device 406 can be a display devicethat includes hardware and/or software for presenting media receivedfrom one or more sources of media content. For example, user device 406can include a television, a smart television, a monitor, a set-top box,an audio video (AV) receiver, any other suitable media playback deviceand/or any suitable combination thereof. More particularly, user device406 can include a display, speakers, hardware and/or software forrendering media content such as analog and/or digital video and/or audiodata, a power supply, etc. User device 406 can, in some embodiments,include various input ports for receiving video and/or audio data fromvarious sources. Such input ports can include one or more HDMI ports,one or more component video ports, one or more composite video ports,one or more USB ports, one or more S-Video ports, one or more TOSLINKports, one or more coaxial ports, one or more Ethernet ports (whetherwired or wireless), etc.

In another more particular example, user device 406 can be any suitabledevice that can receive an audio signal and output the audio signal(potentially through one or more intermediate devices) to one or morespeakers. For example, user device 406 can be an audio video (AV)receiver, a speaker, an amplifier, an audio switch, an HDMI switch, anyother suitable audio system and/or any suitable combination thereof.More particularly, user device 206 can include, speakers, hardwareand/or software for rendering media content such as analog and/ordigital audio and/or video data, a power supply, etc. User device 406can include various input ports for receiving audio and/or video datafrom various sources. Such input ports can include one or more HDMIports, one or more component video ports, one or more composite videoports, one or more USB ports, one or more S-Video ports, one or moreTOSLINK ports, one or more coaxial ports, one or more Ethernet ports(whether wired or wireless), etc. Additionally or alternatively, in someembodiments, user device 406 can be configured to receive an audiosignal over any suitable wireless connection, such as over a connectionto a local area network (e.g., via a connection that complies with oneof the IEEE 802.11x family of protocols which are sometimes referred toas Wi-Fi connections), or a wireless connection between external soundsystem 406 and mobile device 408, such as an ad hoc wireless networkconnection, a short-range wireless communication protocol (e.g.,Bluetooth, Bluetooth Low Energy, Wireless USB, etc.), etc.

Although server 402 is illustrated as one device, the functionsperformed by server 402 can be performed using any suitable number ofdevices in some embodiments. For example, in some embodiments, multipledevices can be used to implement the functions performed by server 402.

Although two user devices 408 and 410 are shown in FIG. 4 to avoidover-complicating the figure, any suitable number of user devices,and/or any suitable types of user devices, can be used in someembodiments.

Server 402 and user devices 406 can be implemented using any suitablehardware in some embodiments. For example, in some embodiments, devices402 and 406 can be implemented using any suitable general-purposecomputer or special-purpose computer. For example, a mobile phone may beimplemented using a special-purpose computer. Any such general-purposecomputer or special-purpose computer can include any suitable hardware.For example, as illustrated in example hardware 500 of FIG. 5, suchhardware can include hardware processor 502, memory and/or storage 504,an input device controller 506, an input device 508, display/audiodrivers 510, display and audio output circuitry 512, communicationinterface(s) 514, an antenna 516, and a bus 518.

Hardware processor 502 can include any suitable hardware processor, suchas a microprocessor, a micro-controller, digital signal processor(s),dedicated logic, and/or any other suitable circuitry for controlling thefunctioning of a general-purpose computer or a special-purpose computerin some embodiments. In some embodiments, hardware processor 502 can becontrolled by a server program stored in memory and/or storage of aserver, such as server 402. In some embodiments, hardware processor 502can be controlled by a computer program stored in memory and/or storage504 of user device 406.

Memory and/or storage 504 can be any suitable memory and/or storage forstoring programs, data, and/or any other suitable information in someembodiments. For example, memory and/or storage 504 can include randomaccess memory, read-only memory, flash memory, hard disk storage,optical media, and/or any other suitable memory.

Input device controller 506 can be any suitable circuitry forcontrolling and receiving input from one or more input devices 508 insome embodiments. For example, input device controller 506 can becircuitry for receiving input from a touchscreen, from a keyboard, fromone or more buttons, from a voice recognition circuit, from amicrophone, from a camera, from an optical sensor, from anaccelerometer, from a temperature sensor, from a near field sensor, froma pressure sensor, from an encoder, and/or any other type of inputdevice.

Display/audio drivers 510 can be any suitable circuitry for controllingand driving output to one or more display/audio output devices 512 insome embodiments. For example, display/audio drivers 510 can becircuitry for driving a touchscreen, a flat-panel display, a cathode raytube display, a projector, a speaker or speakers, and/or any othersuitable display and/or presentation devices.

Communication interface(s) 514 can be any suitable circuitry forinterfacing with one or more communication networks (e.g., computernetwork 404). For example, interface(s) 514 can include networkinterface card circuitry, wireless communication circuitry, and/or anyother suitable type of communication network circuitry.

Antenna 516 can be any suitable one or more antennas for wirelesslycommunicating with a communication network (e.g., communication network404) in some embodiments. In some embodiments, antenna 516 can beomitted.

Bus 518 can be any suitable mechanism for communicating between two ormore components 502, 504, 506, 510, and 514 in some embodiments.

Any other suitable components can be included in hardware 500 inaccordance with some embodiments.

In some embodiments, at least some of the above described blocks of theprocesses of FIGS. 1 and 2 can be executed or performed in any order orsequence not limited to the order and sequence shown in and described inconnection with the figures. Also, some of the above blocks of FIGS. 1and 2 can be executed or performed substantially simultaneously whereappropriate or in parallel to reduce latency and processing times.Additionally or alternatively, some of the above described blocks of theprocesses of FIGS. 1 and 2 can be omitted.

In some embodiments, any suitable computer readable media can be usedfor storing instructions for performing the functions and/or processesherein. For example, in some embodiments, computer readable media can betransitory or non-transitory. For example, non-transitory computerreadable media can include media such as non-transitory forms ofmagnetic media (such as hard disks, floppy disks, and/or any othersuitable magnetic media), non-transitory forms of optical media (such ascompact discs, digital video discs, Blu-ray discs, and/or any othersuitable optical media), non-transitory forms of semiconductor media(such as flash memory, electrically programmable read-only memory(EPROM), electrically erasable programmable read-only memory (EEPROM),and/or any other suitable semiconductor media), any suitable media thatis not fleeting or devoid of any semblance of permanence duringtransmission, and/or any suitable tangible media. As another example,transitory computer readable media can include signals on networks, inwires, conductors, optical fibers, circuits, any suitable media that isfleeting and devoid of any semblance of permanence during transmission,and/or any suitable intangible media.

Accordingly, methods, systems, and media for presenting media contentitems using multiple devices are provided.

Although the invention has been described and illustrated in theforegoing illustrative embodiments, it is understood that the presentdisclosure has been made only by way of example, and that numerouschanges in the details of implementation of the invention can be madewithout departing from the spirit and scope of the invention, which islimited only by the claims that follow. Features of the disclosedembodiments can be combined and rearranged in various ways.

What is claimed is:
 1. A method for presenting media content, the methodcomprising: detecting an offer to initiate a purchase of a content itembeing presented using the media device, wherein the media device has notbeen authenticated with a content service that provides the contentitem; in response to detecting the offer to initiate the purchase of thecontent item when the media device has not been authenticated with thecontent service that provides the content item, causing the media deviceto be discoverable by one or more mobile devices that are connected to asame local area network as the media device; encoding offer datacorresponding to the detected offer to initiate the purchase of thecontent item; in response to receiving a status request from a mobiledevice that is connected to the same local area network as the mediadevice, transmitting the encoded offer data associated with the purchaseof the content item to the mobile device, wherein the encoded offer datacauses a payment user interface to be presented on the mobile device;receiving a cast request from the mobile device to cast the content itemon the media device; and in response to the cast request, executing areceiver application on the media device that accepts the cast requestfrom the mobile device and causes the content item to be presented usingthe media device.
 2. The method of claim 1, wherein the media device isexecuting a media playback application and the mobile device isexecuting a corresponding media playback application, wherein the mediaplayback application transmits the encoded offer data to thecorresponding media playback application executing on the mobile device,and wherein, in response to transmitting the encoded offer data to themobile device, the media device inhibits the transmission of the encodedoffer data to remaining mobile devices that are connected to the samelocal area network.
 3. The method of claim 2, wherein the encoded offerdata is included in an additionalData field.
 4. The method of claim 1,wherein the encoded offer data causes the mobile device to retrievecorresponding human-readable information from a server and wherein thehuman-readable information is presented in the payment user interface onthe mobile device.
 5. The method of claim 1, further comprisingreceiving authentication information from the mobile device, wherein theauthentication information corresponds to a user account that was usedto complete the purchase via the payment user interface on the mobiledevice.
 6. The method of claim 5, wherein the authentication informationcauses the media device to retrieve a corresponding authentication tokenfrom an authentication server, wherein the corresponding authenticationtoken authenticates the user account on the media device.
 7. The methodof claim 1, wherein the cast request indicates that the mobile device isauthorized to play back the content item.
 8. A system for presentingmedia content, the system comprising: a memory; and a hardware processorthat, when executing computer-executable instructions stored in thememory, is configured to: detect an offer to initiate a purchase of acontent item being presented using the media device, wherein the mediadevice has not been authenticated with a content service that providesthe content item; in response to detecting the offer to initiate thepurchase of the content item when the media device has not beenauthenticated with the content service that provides the content item,cause the media device to be discoverable by one or more mobile devicesthat are connected to a same local area network as the media device;encode offer data corresponding to the detected offer to initiate thepurchase of the content item; in response to receiving a status requestfrom a mobile device that is connected to the same local area network asthe media device, transmit the encoded offer data associated with thepurchase of the content item to the mobile device, wherein the encodedoffer data causes a payment user interface to be presented on the mobiledevice; receive a cast request from the mobile device to cast thecontent item on the media device; and in response to the cast request,execute a receiver application on the media device that accepts the castrequest from the mobile device and causes the content item to bepresented using the media device.
 9. The system of claim 8, wherein themedia device is executing a media playback application and the mobiledevice is executing a corresponding media playback application, whereinthe media playback application transmits the encoded offer data to thecorresponding media playback application executing on the mobile device,and wherein, in response to transmitting the encoded offer data to themobile device, the media device inhibits the transmission of the encodedoffer data to remaining mobile devices that are connected to the samelocal area network.
 10. The system of claim 9, wherein the encoded offerdata is included in an additionalData field.
 11. The system of claim 8,wherein the encoded offer data causes the mobile device to retrievecorresponding human-readable information from a server and wherein thehuman-readable information is presented in the payment user interface onthe mobile device.
 12. The system of claim 8, wherein the hardwareprocessor is further configured to receive authentication informationfrom the mobile device, wherein the authentication informationcorresponds to a user account that was used to complete the purchase viathe payment user interface on the mobile device.
 13. The system of claim12, wherein the authentication information causes the media device toretrieve a corresponding authentication token from an authenticationserver, wherein the corresponding authentication token authenticates theuser account on the media device.
 14. The system of claim 8, wherein thecast request indicates that the mobile device is authorized to play backthe content item.
 15. A computer program product containingcomputer-executable instructions that, when executed by a processor,cause the processor to perform a method for presenting media content,the method comprising: detecting an offer to initiate a purchase of acontent item being presented using the media device, wherein the mediadevice has not been authenticated with a content service that providesthe content item; in response to detecting the offer to initiate thepurchase of the content item when the media device has not beenauthenticated with the content service that provides the content item,causing the media device to be discoverable by one or more mobiledevices that are connected to a same local area network as the mediadevice; encoding offer data corresponding to the detected offer toinitiate the purchase of the content item; in response to receiving astatus request from a mobile device that is connected to the same localarea network as the media device, transmitting the encoded offer dataassociated with the purchase of the content item to the mobile device,wherein the encoded offer data causes a payment user interface to bepresented on the mobile device; receiving a cast request from the mobiledevice to cast the content item on the media device; and in response tothe cast request, executing a receiver application on the media devicethat accepts the cast request from the mobile device and causes thecontent item to be presented using the media device.
 16. The computerprogram product of claim 15, wherein the media device is executing amedia playback application and the mobile device is executing acorresponding media playback application, wherein the media playbackapplication transmits the encoded offer data to the corresponding mediaplayback application executing on the mobile device, and wherein, inresponse to transmitting the encoded offer data to the mobile device,the media device inhibits the transmission of the encoded offer data toremaining mobile devices that are connected to the same local areanetwork.
 17. The computer program product of claim 16, wherein theencoded offer data is included in an additionalData field.
 18. Thecomputer program product of claim 15, wherein the encoded offer datacauses the mobile device to retrieve corresponding human-readableinformation from a server and wherein the human-readable information ispresented in the payment user interface on the mobile device.
 19. Thecomputer program product of claim 15, wherein the method furthercomprises receiving authentication information from the mobile device,wherein the authentication information corresponds to a user accountthat was used to complete the purchase via the payment user interface onthe mobile device.
 20. The computer program product of claim 19, whereinthe authentication information causes the media device to retrieve acorresponding authentication token from an authentication server,wherein the corresponding authentication token authenticates the useraccount on the media device.
 21. The computer program product of claim15, wherein the cast request indicates that the mobile device isauthorized to play back the content item.